<html>

<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>-addftr template</title>
</head>

<body bgcolor="#FFFFCC">

<pre>-setattr
template: pers?clnt=&lt;name|pass&gt;&amp;com=setattr&amp;usr=<usr>&amp;<attr_1>=&amp;...
          Order of query params is not important: updates of attribute
          values are performed in the order they appear in the request,
          however the changes are of accummulative nature, so the final
          result is the same.
descript: for the specified user, the value for each specified attribute
          is updated to x , where x is the value corresponding
          to that attribute.
          If no matches are found no records will be updated
          (200 OK will still be returned). If the error
          code 401 is returned then no updates have taken place in the DB.
example : pers?clnt=name|pass&amp;com=setattr&amp;usr=kostas&&amp;lang=GR
returns : 200 OK, 401 (fail, request error), 501 (fail, server error)
200 OK  : in this case the response body is as follows
          &lt;?xml version=&quot;1.0&quot;?&gt;
          &lt;?xml-stylesheet type=&quot;text/xsl&quot; href=&quot;/resp_xsl/rows.xsl&quot;?&gt;
          &lt;result&gt;
          &lt;row&gt;&lt;num_of_rows&gt;number of relevant rows&lt;/num_of_rows&gt;&lt;/row&gt;
          &lt;/result&gt;
comments: the reference to the xsl file allows to view results
          in a web browser. In case the response body is handled
          directly by an application and not by a browser, this
          reference to xsl can be ignored.</attr_1></usr></pre>

</body>

</html>
